home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970626-19970929
/
000213_news@newsmaster….columbia.edu _Thu Aug 21 22:09:42 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id WAA02722
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 21 Aug 1997 22:09:42 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id WAA08588
for kermit.misc@watsun; Thu, 21 Aug 1997 22:09:41 -0400 (EDT)
Path: news.columbia.edu!panix!news.eecs.umich.edu!nntprelay.mathworks.com!howland.erols.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Problem with IF NUMERIC between 3.14 and 3.15
Message-ID: <Gdpy85ilO3pM@cc.usu.edu>
Date: 21 Aug 97 14:04:33 MDT
References: <33fb02f2.277916@news.calvacom.fr>
Organization: Utah State University
Lines: 25
Xref: news.columbia.edu comp.protocols.kermit.misc:7528
In article <33fb02f2.277916@news.calvacom.fr>, do11@calva.net (Dominique Ottello) writes:
> One more time : Hello from France.
>
> The take file hereunder is able to test a keyboard data input to see if the
> data is defined (not only return key), numeric and between lower and upper
> limits.
>
> Under MS-DOS Kermit 3.14 :
> inputs with unary operators + or - are seen as not numeric.
> (The documentation says that only digits 0..9 are accepted)
>
> Under MS-DOS Kermit 3.15 :
> inputs need to have unary operators + or -
> Any data without unary operator + and with more than one numeric character
> is seen as not numeric.
> "5" or "+5" are both seen as numeric
> "12" is seen as not numeric
> "+12" is seen as numeric.
> It seems that the implicit unary operator + is not taken into account.
> == Dominique Ottello == do11@calva.net == Paris == France ==
--------
Your original report was heard directly and the problem (bug) fixed.
A new beta for it has not been issued at this time.
Thanks,
Joe D.